* Set display_priority in ray spec.yaml based on field usage

* Add changelog entry for ray display-priority PR

* Remove unneeded changelog entry (asset-only change)

* Set display_priority in boundary spec.yaml based on field usage

* Add changelog entry for boundary display-priority PR

* Remove unneeded changelog entry (asset-only change)

* Set display_priority in strimzi spec.yaml based on field usage

* Add changelog entry for strimzi display-priority PR

* Remove unneeded changelog entry (asset-only change)

* Set display_priority in kyverno spec.yaml based on field usage

* Add changelog entry for kyverno display-priority PR

* Remove unneeded changelog entry (asset-only change)

…23489)

* Route event bus hook errors through on_error with fail_fast policy

- Introduce HookExecutionError hierarchy (OrchestratorHookError,
  ProcessorHookError) with HookName enum identifying the failed hook.
- Wrap non-Fatal hook failures and route them to the appropriate
  on_error: orchestrator-scope (on_initialize, on_message_received,
  on_finalize) or processor-scope (process_message, on_success).
- Default on_error re-raises so unmodified handlers fall through to
  the new fail_fast orchestrator option.
- FatalProcessingError remains the explicit "stop the bus" signal and
  propagates without going through on_error.

* Add changelog entry for event bus hook error handling

* Address PR feedback: tighten event bus hook error API

- Use StrEnum + auto() for HookName values
- Drop ProcessorSuccessHookError; use ProcessorHookError(ON_SUCCESS) directly
- Type _apply_error_policy handler as Callable[[Exception], Awaitable[None]]

* Address review: SkipMessageError, better diagnostics, fail_fast for ValidationOrchestrator

- Add SkipMessageError raisable from on_message_received to skip dispatch
  for a specific message and continue the loop.
- Drop unused HookName.ON_ERROR.
- Log additional task failures in __process_finished_tasks instead of
  silently abandoning them when several tasks finish in the same batch.
- Include hook name and wrapped error context in the policy log line so
  on_error handler failures are self-contained in the logs.
- Parametrize the orchestrator-hook fail_fast tests over hook_name.
- Set fail_fast=True on ValidationOrchestrator so finalize failures still
  surface in the validation report.
- Expand the changelog with the full list of behavior and API changes.

* Recategorize changelog as 'added' (no external consumers yet)

* Use single backticks in changelog (markdown, not RST)

* Move app.abort() out of ValidationOrchestrator.on_finalize

The orchestrator's on_finalize used to call app.abort() to terminate the
CLI when validations failed. Under the new error policy, click.Exit
raised inside on_finalize is wrapped as a hook failure and surfaces from
run() as an OrchestratorHookError instead of a clean exit.

Move the abort to the CLI command after orchestrator.run() returns:
- Add ValidationOrchestrator.had_failures property.
- on_finalize / _print_console_output no longer raise control-flow
  exceptions.
- 'validate all' calls app.abort() based on had_failures.

* Simplify had_failures with any()

* Spell out BaseProcessor.on_error signature change in changelog

* Update dependency resolution

---------

Co-authored-by: dd-agent-integrations-bot[bot] <dd-agent-integrations-bot[bot]@users.noreply.github.com>

GitHub Actions expressions don't support arithmetic operators, so
`strategy.job-index + 1` made the workflow file invalid. Use the
0-indexed `strategy.job-index` directly.

Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>